Light management system having networked intelligent luminaire managers

ABSTRACT

A network operation center for a light management system having networked intelligent luminaire managers. A plurality of networked luminaire managers, each collocated with a respective luminaire, monitor the status of their respective luminaires. The luminaire managers include transmitters for transmitting status information about their respective luminaires and third-party devices to a network server. The network server forwards the received status information from the networked luminaire managers to a computer of an owner/operator of the plurality of luminaires and/or a third-party user. The luminaire managers communicate with each other, whereby they form a network.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/028,597, filed on Feb. 8, 2008, which itself is a continuation ofU.S. patent application Ser. No. 11/518,495, filed Sep. 11, 2006,entitled “Light Management System Having Networked Intelligent LuminaireManagers with Enhanced Diagnostics Capabilities,” which issued as U.S.Pat. No. 7,333,903, which claims the benefit of U.S. Provisional PatentApplication No. 60/715,584, filed on Sep. 12, 2005, each of which isincorporated herein by reference in its entirety.

This application is related to the following commonly owned patentapplications: (1) U.S. patent application Ser. No. 11/518,497, filedSep. 11, 2006, entitled “Light Management System Having NetworkedIntelligent Luminaire Managers”, which issued as U.S. Pat. No.7,603,184; (2) U.S. patent application Ser. No. 11/518,496, filed Sep.11, 2006, entitled “Light Management System Having Networked IntelligentLuminaire Managers That Support Third-Party Applications”, which issuedas U.S. Pat. No. 7,911,359; (3) U.S. patent application Ser. No.11/518,488, filed Sep. 11, 2006, entitled “Network Operation Center ForA Light Management System Having Networked Intelligent LuminaireManagers”, which issued as U.S. Pat. No. 7,546,167; (4) U.S. patentapplication Ser. No. 11/518,494, filed Sep. 11, 2006, entitled“Owner/Operator Control Of A Light Management System Using NetworkedIntelligent Luminaire Managers”, which issued as U.S. Pat. No.7,546,168; and (5) U.S. patent application Ser. No. 11/518,511, filedSep. 11, 2006, entitled “Activation Device For An Intelligent LuminaireManager”, which issued as U.S. Pat. No. 7,529,594; each of which isincorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The present invention generally relates to light system management. Moreparticularly, it relates to controlling and managing outdoor lightingunits using a light management system having networked intelligentluminaire managers, and applications thereof.

BACKGROUND OF THE INVENTION

It is estimated that there are more than 60 million outdoor lights inthe United States autonomously controlled by conventionalphoto-controls. These outdoor lights, when properly working, simplyreact to ambient light conditions, for example, to turn-on at dusk andturn-off at dawn. This method of operating outdoor lights results inmany lights being on when they are not needed, and it significantlyincreases outdoor lighting system operating costs.

The use of conventional photo-controls to control outdoor lights(luminaires) also leads to maintenance and repair issues. There aresignificant costs associated with hiring qualified maintenance personneland buying equipment such as, for example, special maintenance vehiclesrequired to access light fixtures for replacing lamps and servicingelectrical components. To discover faulty fixture operations, lightsystem owners and operators must resort to sending maintenance personnelto do “drive-by” visual examination of all units, which often number inthe thousands or wait for a customer to report a malfunction. Thisdrive-by must be done at night to detect non-functioning fixtures. Thesehigh costs limit how many lights can be repaired or serviced on anygiven day and force many light system operators to maintain theiroutdoor lights on an as needed basis (i.e., only when they are notifiedof an inoperable light). Understandably, this maintenance methodology ishighly inefficient because it ties up resources as crews and equipmentrandomly travel to failed, geographically dispersed outdoor lights.

Lighting system operators (e.g., electric utilities) have tried to limitthe time, equipment, and personnel spent on any given outdoor light byconducting group maintenance programs, where lights within a givengeographical area are maintained on a scheduled basis. This approachreduces travel time between lights. In order to implement thismaintenance methodology, light system operators must estimate lightingequipment life expectancy and schedule maintenance in each geographicalarea when lighting outages in the area are expected to reach apredetermined level. While this methodology has certain benefits,maintenance crews often replace good equipment that has significantadditional life remaining Consequently, this maintenance methodologyresults in maintenance crews throwing away good equipment and visitingoutdoor lights that do not require maintenance. Locating light fixtureswith failed lamps is a problem since roadway fixtures are only on atnight and most maintenance crews work during the day.

What is needed is a new light management system that overcomes thedeficiencies noted above.

BRIEF SUMMARY OF THE INVENTION

The present invention provides a light management system havingnetworked intelligent luminaire managers, and applications thereof. Inan embodiment, a plurality of networked luminaire managers, eachcollocated with a respective luminaire, monitor the status of theirrespective luminaires. Each luminaire manager includes a transmitter fortransmitting status information about its respective luminaire such as,for example, a lamp out condition upon occurrence of such a lamp outcondition, to a network server. The network server forwards the receivedstatus information from the networked luminaire managers to a computerof a light system owner/operator. The luminaire managers communicatewith each other, whereby they form a network.

Features and advantages of the present invention, as well as thestructure and operation of various embodiments of the present invention,are described in detail below with reference to the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The accompanying drawings, which are incorporated herein and form partof the specification, illustrate the present invention and, togetherwith the description, further serve to explain the principles of theinvention and to enable persons skilled in the pertinent arts to makeand use the invention.

In the drawings, like reference numbers indicate identical orfunctionally similar elements. Additionally, the left-most digit of thereference number indicates a drawing in which the reference number firstappears.

FIG. 1 is a diagram illustrating a light management system according toan embodiment of the present invention.

FIG. 2 is a diagram illustrating street lights networked together usingintelligent luminaire managers according to an embodiment of the presentinvention.

FIG. 3A is a diagram illustrating an intelligent luminaire manageraccording to an embodiment of the present invention.

FIG. 3B is a block diagram illustrating a luminaire and the intelligentluminaire manager of FIG. 3A according to an embodiment of the presentinvention.

FIG. 3C is a circuit diagram illustrating a luminaire and theintelligent luminaire manager of FIG. 3A according to an embodiment ofthe present invention.

FIG. 3D is a circuit diagram further illustrating the intelligentluminaire manager of FIG. 3A according to an embodiment of the presentinvention.

FIG. 3E is a flow chart illustrating the steps of a method for detectingcycling according to an embodiment of the present invention, which isimplemented by embodiments of the intelligent luminaire manager of FIG.3A.

FIG. 3F is a flow chart illustrating the steps of a method for detectinga bad lamp according to an embodiment of the present invention, which isimplemented by embodiments of the intelligent luminaire manager of FIG.3A.

FIG. 3G is a flow chart illustrating the steps of a method for detectinga bad fixture according to an embodiment of the present invention, whichis implemented by embodiments of the intelligent luminaire manager ofFIG. 3A.

FIG. 3H is a flow chart illustrating the steps of a method forpredicting lamp failure according to an embodiment of the presentinvention, which is implemented by embodiments of the intelligentluminaire manager of FIG. 3A.

FIG. 3I is a graph illustrating fixture power as a function of timeduring startup of a gas discharge lamp.

FIG. 4A is a diagram illustrating a network operation center accordingto an embodiment of the present invention.

FIG. 4B is a diagram illustrating geographically distributed networkoperational centers according to an embodiment of the present invention.

FIG. 5A is a diagram illustrating a light system owner/operatoraccording to an embodiment of the present invention.

FIG. 5B is a diagram illustrating an intelligent luminaire manager fieldunit according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides a light management system havingnetworked, intelligent luminaire managers, and applications thereof. Inthe detailed description of the invention that follows, references to“one embodiment”, “an embodiment”, “an example embodiment”, etc.,indicate that the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to effect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described.

FIG. 1 illustrates a light management system 100 having networkedintelligent luminaire managers 112 according to an embodiment of thepresent invention. As illustrated in FIG. 1, light management system 100includes networks 102 a and 102 b, a network operation center 106, lightsystem owner/operators 108 a and 108 b, and third-party users 110. Thesesubsystems of system 100 are linked together using appropriatecommunication means such as, for example, radio frequencycommunications, optical communications and/or power line carrier to formcommunications backbone 104.

Each of the networks 102 a and 102 b includes several intelligentluminaire managers (ILMs) 112 and a master control 114. The intelligentluminaire managers 112 communicate with each other and with mastercontroller 114 using, for example, short-range radio frequency (RF)communication links. In an embodiment, these RF communication linksoperate in the 900 MHz unlicensed band and have a range of about 1000feet. As described further below with reference to FIGS. 2 and 3, eachof the intelligent luminaire managers 112 controls operation of a lightfixture, also called a luminaire.

Networks 102 a and 102 b in FIG. 1 each monitor and control operation ofan outdoor light system or subsystem. These outdoor light systems arerepresented as being operated and maintained by light systemowner/operators 108 a and 108 b respectively. Accordingly, datacollected by intelligent luminaire managers 112 regarding the status ofthe light system represented by network 102 a is forwarded toowner/operator 108 a. Data collected by intelligent luminaire managers112 regarding the status of the light system represented by network 102b is forwarded to owner/operator 108 b. Owner/operators 108 a and 108 balso have the capability to send commands to and/or reprogram operationof the intelligent luminaire managers coupled to their lights using thedata network shown in FIG. 1. This allows owner/operators 108 a and 108b to adjust the operation of their respective light system.

In preferred embodiments of the present invention, networks 102 arepeer-to-peer networks and/or mesh networks. These networks support threelevels of devices: master controllers 114; network routing devices, forexample, intelligent luminaire manager 112; and other nodes such as RFdevice 202 (see FIG. 2).

Each of the network links between intelligent luminaire managers 112includes a two-way communication channel. These two-way communicationchannels between intelligent luminaire managers 112 support, forexample, over the air or power-line carrier re-keying and re-programmingof these intelligent control device. This allows for on-demand, turn-onand turn-off, for example, of selected street lights coupled tointelligent luminaire managers 112.

In an embodiment, each intelligent luminaire manager 112 maintains aninternal clock which is synchronized throughout the entire network. Theclock may be local to the device or maintained at a selected locationand transmitted to each luminaire manager 112. This permits accuratedate/time stamps to be added to data sent to network operations center106 and for time-based control of intelligent luminaire managers 112.

In embodiments of the present invention, intelligent luminaire managers112 support commands sent from master controller 114 to alternaterouting paths. Additionally, intelligent luminaire managers 112 willautomatically attempt to reconnect to network 102 if a signal is lostfor more than a selected period of time (e.g., after 15 minutes, after30 minutes, after 60 minutes, etc.). Each intelligent luminaire manager112 is capable of rerouting data through an alternative path, should oneor more of the intelligent luminaire managers 112 fail. When a failed ornew intelligent network controller 112 reenters network 102, otherdevices within the network pass on the activation or installation of thenew intelligent luminaire manager to other network routing devices.

Additional details about the operation of intelligent luminaire managers112 are described below.

Master controllers 114 a and 114 b serve as gateways between theirassociated intelligent luminaire managers 112 and network operationcenter 106. Each master controller 114 is coupled to network operationcenter 106 through a communication backbone channel 104. In embodiments,communication backbone channels 104 can be, for example, electricaland/or optical land line communication channels, satellite communicationchannels, paging network channels, power line carrier channels, RF linksand/or cellular communication channels. These communication channels caninclude public and/or private communication means (e.g., utility ownedlines and/or the Internet).

In one embodiment, network operation center 106 couples to mastercontrollers 114 via an internet protocol infrastructure provided bythird party carrier network services. Master controllers 114 preferablyprovide data concentration and compression, and thereby reduce theoverall service fees for third party leasing arrangements ofcommunication services. Master controllers 114 also preferably include adata storage capability so that data to and from intelligent luminairemanagers 112 can be stored during network communication disruptions andtransmitted after communications are restored.

In an embodiment, each master controller 114 connects with networkoperation center 106 at predetermined times and uploads the currentstatus of all intelligent luminaire managers 112 within its area ofresponsibility and any devices that have entered network 102 since itslast update to network operations center 106. For high-prioritycommunications, such as, for example, detection of a failed lamp, mastercontroller 114 may make unscheduled communications to network operationcenter 106.

Preferably, each master controller 114 is responsible for linkingseveral intelligent luminaire managers 112 to network operation center106. For example, in one embodiment, more than 500 intelligent luminairemanagers may be linked by a single master controller 114 to networkoperation center 106. It is a feature of each master controller 114 thatit can be programmed from network operation center 106.

In certain embodiments, master controller 114 is capable of inheritingthe features of network 102 routing devices, such as intelligentluminaire manager 112, for communications within network 102. Mastercontroller 114 also can implement, for example, a TCP/IP stack forcommunications over communication backbone channel 104 with networkoperation center 106. Master controller 114 preferably includes memorysuch as card slot non-volatile storage or compact flash memory andcaches data representing the status of all intelligent luminairemanagers 112 for which it is responsible.

As described in more detail below, in embodiments, master controller 114provides authentication and authorization to radio frequency deviceswanting to enter network 102. Master controller 114 communications withintelligent luminaire managers 112 and optimizes routing within itsnetwork cluster. Master controller 114 also preferably includes a backupenergy source sufficient to power master controller 114, for example,for up to 24 hours of operation.

Network operation center 106 provides a variety of services for lightsystem owner/operators 108. These services include, for example,24-hour-a-day, seven-day-a-week data storage and forwarding services fordata flowing between light system owner/operators 108 and theirrespective intelligent luminaire managers 112. Network operation center106 is preferably responsible for configuring, monitoring, and operatingthe router switches and other communication equipment that comprise thedata network illustrated by FIG. 1. In an embodiment, network operationcenter 106 manages and allocates internet protocol addresses and domainnames for the data network, manages and allocates nodes for the datanetwork, provides database management services, network securitymanagement, and other network services.

As illustrated in FIG. 1, network operation center 106 interfaces with aplurality of light system owner/operators 108 and/or other appropriateentities. Each light system owner/operator is shown comprising a lightsystem manager 109 and a maintenance unit 111. Maintenance personnel 120from the maintenance units are responsible for repairing, replacing andmaintaining their own respective light systems. Maintenance personnel120 may also be responsible for initial installation and activation oftheir intelligent luminaire managers 112 with the aid of a wirelessdevice such as a personal data assistant (PDA) hosted, intelligentluminaire manager field unit 122, or another microprocessor baseddevice. This field unit is described in more detail below with referenceto FIGS. 5A and 5B.

In operation, system 100 performs as illustrated by the followingexample cycle of events. An owner/operator 108 of an outdoor lightsystem wishes to reduce operation and maintenance costs associated withhis or her light system. The owner/operator 108 therefore hasmaintenance personnel 120 install and activate intelligent luminairemanagers 112 according to the present invention on each of the lights ofthe light system, for example, as the conventional photo-controls arereplaced due to failures. A master controller 114 is also installed inthe vicinity of one of the intelligent luminaire managers (e.g., on anearby pole or building rooftop).

During the installation and activation of each intelligent luminairemanager, selected information such as the intelligent luminairemanager's identification number, GPS grid coordinates for the locationof the installation, the type of light equipment being controlled, adigital photo of the installation, and/or initial equipment parametersis collected by maintenance personnel 120 with the aid of the PDA hostedfield unit 122. This information is then stored in the owner/operator'smaintenance system records. In embodiments, the PDA hosted field unit122 can communicate with intelligent luminaire managers 112 as well asmaster controllers 114 to receive information and/or upload information.

Using the services of network operation center 106 and a computerconnected to network operation system 106 (e.g., via a secure Internetlink), owner/operator 108 is able to monitor and control his or herlights. For example, if a light fails or is determined to be degraded,the intelligent luminaire manager 112 coupled to the light sends analarm to owner/operator 108, indicating that a failure has occurred oris likely to occur, via the network and network operation center 106.This alarm notifies light system owner/operator 108 of the changed lightsystem status and allows owner/operator 108 to take appropriate action.

In one embodiment, the alarm interacts automatically with theowner/operator's maintenance program and generates a work order thattells maintenance personnel 120 what actions are needed. The work ordermight include, for example, the time of the alarm, the location of thedegraded or failed equipment, and what equipment or parts are needed tocorrect the problem that caused the alarm. This work order isdown-loaded into the PDA-hosted intelligent luminaire manager field unitand used to guide maintenance personnel 120 to the site of the degradedor failed equipment. Once the repairs to the light are made, intelligentluminaire manager 112 updates the status for the light and the alarm iscleared. In an alternative embodiment, the alarm is cleared only whenowner/operator 108 updates his or her maintenance records, for example,using data collected by the intelligent luminaire manager field unit 122while the repair was being performed. In another embodiment, failure isonly reported to owner/operator 108 when the failure has occurred aspecified number of days in a row.

Once owner/operator 108 has installed intelligent luminaire managers onhis or her lights, owner operator 108 can control when the lights areturned-on and turned-off. This is achieved by sending commands over thedata network to individual or assignable groups of intelligent luminairemanagers 112 and/or reprogramming a control program stored in a memoryof each intelligent luminaire manager or group of assignable intelligentluminaire managers. More details regarding the functionality ofintelligent luminaire managers 112 is provided below.

Also shown in FIG. 1 are third-party users 110. Third-party users 110are managers/users of system 100 other than light system owner/operators108 and network operation center 106 personnel. For example, a thirdparty user 110 may be someone hired by an owner/operator 108 to operatehis or her light system or someone who is leasing, or otherwiseappropriately using, bandwidth in system 100 as explained in more detailbelow with reference to FIG. 2.

FIG. 2 illustrates a plurality of street lights 200 that form part of alight system operated and maintained by an owner/operator 108. Eachstreet light 200 is equipped with an intelligent luminaire manager 112mounted, for example, on top of a light fixture 204 of street lamp 200.In the embodiment shown, intelligent luminaire manager 112 is preferablyconfigured and housed in an enclosure that conforms to appropriate NEMAand ANSI standards so that it can be exchanged one-for-one with aprior-existing photo-control used to control light fixture 204. Thiscompatibility allows intelligent luminaire manager 112 to be installedon a light fixture 204 without requiring a new mount and withoutrequiring any rewiring or physical modification of the fixture. Personsskilled in the relevant arts are familiar with industry standards suchas NEMA and ANSI C136 standards, and they will understand, based on thedisclosure herein, how to adapt intelligent luminaire manager 112 forselected applications and customers.

As shown in FIG. 2, an intelligent luminaire manager 112 communicatesusing an RF communication link with its neighbors mounted on neighboringstreet lights 200. In an embodiment, an intelligent luminaire manager112 also is capable of communicating with other nearby devices thatinclude, for example, an RF device 202. This communication can beunidirectional or bidirectional. The unidirectional communication can befrom RF device 202 to intelligent luminaire manager 112 or fromintelligent luminaire manager 112 to RF device 202 depending on whetherRF device 202 is a transmitting device or a receiving device.Communication with an RF device 202 is established when an RF device 202enters into the communication space of an intelligent luminaire manager112 and is authorized to become a part of the network formed byintelligent luminaire manager 112 and its neighbors.

In one embodiment, RF device 202 may become a part of a network bytransmitting a signal that is received by a communications unit insideintelligent luminaire manager 112. Intelligent luminaire manager 112then reports the presence of RF device 202 to network operation center106, via the network and a master control 114. RF device 202 may beallowed to simply transmit data over the network, or it may be allowedto transmit and receive data. This communication can be either open orencrypted. Intelligent luminaire manager 112 is able to blockcommunications from RF device 202 if RF device 202 is assessed to befunctioning improperly or if the RF device's access is denied based on ablacklist maintained by the network operations center or if the RFdevice is interfering with the routing of higher priority traffic.

In embodiments of the present invention, RF device 202 is referred to asa blind slave. A blind slave is a device controlled by intelligentluminaire manager 112. One example use of a blind slave is to controlthe operation of an outdoor light (e.g., a house porch light or adriveway light). The blind slave coupled to the light receives commandsfrom a nearby intelligent luminaire manager 112 to turn-on and turn-offthe light, for example, in conjunction with the luminaire controlled bythe intelligent luminaire manager 112. In one embodiment, blind slavesmay be controlled by a utility in order to limit power usage duringperiods of high power demand and thereby prevent brown-outs orblack-outs from occurring. The use of blind slaves is not limited tojust photo control.

In embodiments of the present invention, the communication links betweenintelligent luminaire managers 112 can include, for example, power linecarrier communication links or optical communication links. Thus, thepresent invention is not limited to using only RF communication links.

As described further below with reference to FIG. 6, the preciselocation of each intelligent luminaire manager device 112 is known.Therefore, using appropriate algorithms, intelligent luminaire manager112, master controller 114 and/or network operation center 106 are ableto accurately determine and report the location of any RF device 202.For example, in an embodiment of the present invention, mastercontroller 114 is able to calculate interpolated coordinates for an RFdevice 202 based on information received from a variety of intelligentluminaire managers 112 and the master controller's knowledge of thelocations of these luminaire managers 112.

As will be understood by persons skilled in the relevant arts, thepotential for communicating with radio frequency (RF) or radio frequencyidentification (RFID) type devices using the network formed byintelligent luminaire managers 112 is nearly boundless and limited onlyby the bandwidth available. For example, an RF device 202 might beincluded in a car and used to monitor and locate stolen cars as theypass by or park near streetlights 200. An auto insurance company can paya light system owner/operator to monitor for and report the location ofstolen cars using his or her network. In this example, an RF device 202might be configured to start transmitting a stolen car signal, forexample, whenever the car's engine was started without using the car'signition key. This stolen car signal would be detected by an intelligentluminaire manager 112 and reported via the network to an appropriateindividual (e.g., a third party user 110 such as an insurance companyrepresentative and/or a local law enforcement official).

A similar use to that described above of the network capabilities ofintelligent luminaire managers 112 would be to identify and locate anindividual under house arrest, wearing an ankle bracelet, who has lefthis or her house. Other possible uses include, but are not limited to:providing security monitoring to determine if a nearby gate is open orclosed or whether a particular system is on or off; to provide aninterface to General Motor's ON-STAR system; to provide gun shotdetection; to provide auto traffic and pedestrian monitoring; to providepublic address audio communications and broadcast warning information(e.g., radiation alerts, bio alerts, chemical alerts, smog alerts,etc.); to provide high crime area surveillance; to locate lostindividuals, children and pets; to relay weather monitoring data, powermonitoring data, etc.; to repeat cellular communications, WiFicommunications, or Internet communications; and to read and/or relayelectric meter data, gas meter data, and/or water meter data for publicutilities. Still other uses will become apparent to those skilled in therelevant arts given the description herein.

FIG. 3A shows a detailed view of an enclosure 301 for intelligentluminaire manager 112 according to an embodiment of the invention. Asshown in FIG. 3A, housing 301 of intelligent luminaire manager 112includes a window 303 that exposes a photo-detector 305 to ambientlight. This allows intelligent luminaire manager 112 to be programmed toturn-on and/or to turn-off based on ambient light conditions in additionto an internal clock. A filter can be used to adjust thesensitivity/response of photo-detector 305 (e.g., a filter such as aninfrared filter can be used to prevent the unwanted turning-on andturning-off of a light due to passing clouds, sky condition or theinfluence of other nearby lights).

In an embodiment, intelligent luminaire manager 112 includes at leastone LED (not shown) internal or external to enclosure 301 forcommunicating with maintenance crews. In one embodiment, the LEDtransmits infrared signals that are received by PDA hosted field unit122. In another embodiment, the LED flashes a visual code that can beseen and interpreted by the maintenance crew. For example, when anintelligent luminaire manager is initially installed, it sends a messageto a nearby intelligent luminaire manager 112 and receives back anacknowledgement signal. When this acknowledgment signal is received bythe newly installed intelligent luminaire manager 112, its LED sends orflashes a code to let the maintenance crew know that the signal has beensent and an acknowledgement signal received. This lets the maintenancecrew know that the intelligent luminaire manager 112 is workingproperly. In an embodiment, an LED signal may be different colors toindicate different status.

As noted above, enclosure 301 preferably conforms to appropriate NEMAand ANSI standards so that is can be installed on an intended lightfixture without requiring a new mount and without requiring any rewiringor physical modification of the fixture. In embodiments, enclosure 301is formed from a highly durable material, such as plastic, that isappropriate for outdoor use and that will withstand the expected weatherand temperatures variations at the intended location of installation.Enclosure 301 also can be coated with a weather-resistant material.

In an embodiment, each luminaire manager 112 or enclosure 301 has ascannable barcode securely attached for purposes of identification. Anidentification code can also be stored in a memory of each luminairemanager 112. In an embodiment, PDA hosted field unit 122 is used to readand/or write the identification code to the memory of each luminairemanager 112.

FIG. 3B is a block diagram that further illustrates the features andfunctionality of an intelligent luminaire manager 112 according to anembodiment of the present invention. As shown in FIG. 3B, intelligentluminaire manager 112 is coupled to and controls a light or moreprecisely a luminaire 200. Luminaire 200 includes a ballast 302, astarter 306, and a lamp 308. Intelligent luminaire manager 112 includesa controller 310, a luminaire condition sensing and diagnostic subsystem312, a communications subsystem 314, and other optional subsystems 316.

In an embodiment, luminaire 200 is a conventional luminaire such as, forexample, a street light. The purpose and function of ballast 302,starter 306, and lamp 308 are well-known to persons skilled in therelevant art.

Controller 310 includes a processor 318, memory 320, and an interfacesubsystem 322. Memory 320 stores a variety of programs that are executedand/or implemented using processor 318. These programs include, forexample, a luminaire control program 324, luminaire and intelligentluminaire manager configuration program 326, status reporting program328, and other optional programs 330.

As will become apparent to persons skilled in the relevant arts giventhe description herein, intelligent luminaire manager 112 is a novel andenhanced networking device that includes and improves upon thefunctionality and capabilities of the luminaire diagnostic system(s)described in U.S. Pat. Nos. 6,028,396, 6,452,339, and 6,841,944, each ofwhich is incorporated herein by reference in its entirety. Theseimprovements are described below.

One notable improvement is added functionality that allows intelligentluminaire manager 112 to be used to turn-on and turn-off lamp 308 ondemand. Commands to turn-on and turn-off lamp 308 can be delivered tointelligent luminaire manager 112 via the data network illustrated inFIG. 1. In an embodiment, data sent by an owner/operator 108 over thenetwork is used to program a luminaire control program 324 stored inmemory 320 of intelligent luminaire manager 112. This program interactswith a network synchronized clock/timer function and supports an on-timeand an off-time for lamp 308 for each day of the week with a one-minutetime resolution. Example on-time and off-time commands that can beprogrammed include: (1) turn on lamp 308 at time X, and turn off lamp308 at time Y; (2) turn on lamp 308 at time X, and turn off lamp 308 Yminutes after it is turned on; (3) turn on lamp 308 at dusk, and turn itoff X minutes after it turns-on; and (4) turn on lamp 308 at dusk, andturn it off X minutes after dawn.

The above described programmable commands to turn-on and turn-off lamp308 are illustrative only and not intended to limit the presentinvention. Other programmable commands that can be used will becomeapparent to persons skilled in the relevant arts given the descriptionherein. For example, commands can be programmed to turn lamp 308 on onlyduring certain days of the week, to turn-on and turn-off lamp 308 atdifferent times during different days in a given week, or all lamps in agroup can be turned-on at a specified time and turned-off, for example,at dawn. In one embodiment, selected lamps can be sent a command toturned-off during periods of high power demand. Likewise, turn-on andturn-off times can be programmed to meet state or local light trespasscodes, and these can be re-programmed remotely if the light trespasscodes change.

In one embodiment, in the event an intelligent luminaire manager 112loses contact with network operations center 106 or master controller114, due for example to a network failure, intelligent luminaire manager112 will revert to a pre-stored program for controlling luminaire 200.For example, this could be to turn on lamp 308 at dusk and to turn itoff at dawn. Intelligent luminaire manager 112 can tolerate and continueoperating through expected energy surges and sags without disruption ofoperation.

In an embodiment, an intelligent luminaire manager 112 uses luminairecondition sensing and diagnostic subsystem 312 to monitor A/C powerprovided to luminaire 200. For example, luminaire condition sensing anddiagnostic subsystem 312 monitors voltage sags and over voltage andrecords the time, severity, and duration of these events, and reportsthese events to owner/operator 108. Additionally, in an embodiment,luminaire condition sensing and diagnostic subsystem 312 records thecurrent provided to start lamp 308 and the current drawn by lamp 308 atsome period after it is lit. Such data is useful, for example, formonitoring the proper operation of luminaire 200, and in particularballast 302.

In one example embodiment, intelligent luminaire manager 112 monitorscycling of luminaire 200. It records, for example, fixture current afterlamp 308 starts. If the fixture current increases or decreases more thana specified amount in a given time interval, this denotes one cycle.Cycle detections are reported to the master controller 114, via networkmessages, and forwarded to owner/operator 108. In one embodiment, anoccurrence of multiple cycles such as, for example, about five in agiven night may be reported as a defective lamp.

In an embodiment, intelligent network luminaire manager 112 generates afaulty lamp signal/alarm in the following manner. First, it measureslamp 308 power or volt amperes at two seconds after start, 15 secondsafter start, one minute after start, and 8.5 minutes after start. If allfour measurements are the same within, for example, about 10%, lamp 308is flagged as faulty. Accordingly, a faulty lamp detection signal/alarmis stored and relayed to network operation center 106 and owner/operator108.

As noted herein, values such as the 10% tolerance for currentcomparisons are reprogrammable. However, loss of network connectivity,for example, for more than a selected period of time causes intelligentluminaire manager 112 to revert programmable time measurement intervalsand tolerances to default values stored within intelligent luminairemanager 112 memory.

Intelligent luminaire manager 112 is preferably capable of measuringtrue AC currents and voltages in addition to average currents andvoltages. In embodiments, intelligent luminaire manager 112 determinesand records the power consumption of an attached device as well as powerfactor and load.

As described above, status data collected by intelligent luminairemanagers 112 is communicated via network 102 to master controller 114and then to network operation center 106. At network operation center106, the status data is analyzed for alarms and alerts, sorted, stored,and routed to an appropriate owner/operator 108.

Additional features and functionality of intelligent luminaire manager112 are described below.

FIG. 3C is a circuit diagram that further illustrates luminaire 200 andintelligent luminaire manager 112 according to an embodiment of thepresent invention. The circuit diagram is illustrative and not intendedto limit the present invention. As shown in FIG. 3C, in one embodiment,intelligent luminaire manager 112 is a three-prong device per ANSIC136.10 or similar standard that acts like a switch to control the powersupplied to luminaire 200. A first prong 301 a of intelligent luminairemanager 112 connects to an energized line of a power supply (not shown).A second prong 301 b of intelligent luminaire manager 112 connects to aneutral line or common of the power supply. A third prong 301 c ofintelligent luminaire manager 112 connects to a load line of luminaire200. The load line is attached to ballast 302 and an optional powerfactor correction capacitor 304. Ballast 302 is connected to starter 306(if used) and lamp 308. Optional power factor correction capacitor 304,starter 306, and lamp 308 are each connected to the neutral line of thepower supply.

FIG. 3D is a more detailed circuit diagram of an intelligent luminairemanager 112 according to an embodiment of the present invention. Asshown in FIG. 3D, power from the power supply is rectified by arectifier 350. Rectified power is filtered and regulated, and providedto controller 310. In an embodiment, controller 310 is a commerciallyavailable microprocessor or microcontroller. Rectified power is alsoprovided to a pickup coil 354 of a relay 352. When a control signalprovided by controller 310 closes a switch 356, pickup coil 354 isenergized and closes a contact of relay 352. As illustrated in FIG. 3C,the closing of the relay contact provides power to luminaire 200.

As shown in FIG. 3D, two resistances 358 and 359 form a voltage dividernetwork. The voltage developed across resistance 359 is a referencevoltage (Vref) that is provided to controller 310 as an input parameter.A current sensor 357 is coupled between relay 352 and the load prong ofintelligent luminaire manager 112. Current sensor 357 generates areference current (Iref), which is also provided to controller 310 as aninput parameter. In one embodiment, current sensor 357 is a currenttransformer. In another embodiment, current sensor 357 is a currentsensing resistor or Hall effect sensor. As described below in moredetail, the input parameters Vref and Iref are used to diagnose andprovide an indication of the status of luminaire 200.

FIG. 3E is a flow chart illustrating the steps of a method 360 fordetecting cycling according to an embodiment of the present invention.Method 360 can be implemented by embodiments of intelligent luminairemanager 112. As shown in FIG. 3E, method 360 comprises steps 361-367.

In step 361, the input AC voltage (V.sub.AC) provided to a luminaire ismeasured. In an embodiment, the input AC voltage is preferably measuredat a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The frequency (.omega.) of theinput AC voltage can be determined, for example, by identifying how manyvoltage waveform zero-crossings occur in a selected time interval.

In step 362, the input AC current (I.sub.AC) provided to the luminaireis measured. In an embodiment, the input AC current is also preferablymeasured at a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The phase angle (.theta.)between the measured AC current and the AC voltage measured in step 361can be determined, for example, by determining a time difference betweenthe current waveform zero-crossing and the voltage waveformzero-crossing.

In step 363, a ratio between real power and apparent power is calculated(e.g., real power divided by apparent power). Both real power andapparent power are determined based on the AC voltage measurements fromstep 361 and the AC current measurements from step 362. Example ratiosof real power divided by apparent power range from about 1 to about lessthan 0.1. For example, a properly working, non-power-factor-correctedluminaire having a reactor ballast and a 100 watt high pressure sodiumlamp has a real power of about 120 watts and an apparent power of about200 VA. This results in a ratio of 120/200 or 0.6. Apower-factor-corrected luminaire having a reactor ballast and a 100 watthigh pressure sodium lamp has a real power of about 120 watts and anapparent power of about 120 VA. This results in a ratio of 120/120 or 1.

In step 364, a determination is made whether the AC current is greaterthan or equal to a first threshold value. This check is performed, forexample, to make sure the lamp is lit. In an embodiment, the firstthreshold value is about one amp. Other values can also be used. If theAC current is greater than or equal to a first threshold value, controlpasses to step 365. Otherwise, control passes to step 366.

In step 365, a determination is made whether the ratio of real power toapparent power calculated in step 363 is less than or equal to a secondthreshold value. The second threshold value can be selected, forexample, based on the particular luminaire (e.g., fixture type and lamptype) to be monitored, or it can be a more general value that isselected to work with multiple luminaires (e.g., various combinations offixture types and lamp types). For example, a value of 0.4 could beselected to monitor both a non-power-factor-corrected luminaire having areactor ballast and a 100 watt high pressure sodium lamp and apower-factor-corrected luminaire having a reactor ballast and a 100 watthigh pressure sodium lamp. If the ratio calculated in step 363 is lessthan the second threshold value, control passes to step 367 (LampCycling). Otherwise, control passes to step 366.

Persons skilled in the relevant arts will know how to select a secondthreshold value given the description herein. It is a feature of method360 that in step 365 cycling can be detected for a wide variation ofluminaires (e.g., luminaires having lamps with an operating power ofabout 70 watts to about 1000 watts).

In step 366, a determination is made whether there has been a change inthe AC current that is greater than or equal to a third threshold value.For example, in one embodiment, a determination is made after lampstartup whether the current measured in step 362 has increased ordecreased more than about 25% in a one second interval. If there hasbeen a 25% change in current, the lamp is identified as cycling unless,for example, there was an interruption in AC power. Other thresholdvalues can be used, and persons skilled in the relevant arts will knowhow to select a third threshold value given the description herein. Thistest works well, for example, with luminaires having lamps with anoperating power of about 70 watts to about 400 watts. If the change inAC current is greater than or equal to the third threshold value,control passes to step 367 (Lamp Cycling). Otherwise, control passes tostep 361.

In step 367, a signal is generated to indicate that the lamp has cycled.In certain applications, a counter may be used to keep track of how manytimes a lamp has cycled, for example, during a single night. Once apredetermined number of cycles have occurred, power to the lamp may beswitched off to prevent damage of the luminaire.

As will be understood by persons skilled in the relevant art, method 360can be modified, for example, to delete one of the two depicted cyclingtests or to add additional cycling tests.

FIG. 3F is a flow chart illustrating the steps of a method 370 fordetecting a bad lamp of a luminaire according to an embodiment of thepresent invention. Method 370 can be implemented by embodiments ofintelligent luminaire manager 112. As shown in FIG. 3F, method 370comprises steps 371-375.

In step 371, the input AC voltage (V.sub.AC) provided to a luminaire ismeasured. In an embodiment, the input AC voltage is preferably measuredat a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The frequency (.omega.) of theinput AC voltage can be determined, for example, by identifying how manyvoltage waveform zero-crossings occur in a selected time interval.

In step 372, the input AC current (I.sub.AC) provided to the luminaireis measured. In an embodiment, the input AC current is also preferablymeasured at a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The phase angle (.theta.)between the measured AC current and the AC voltage measured in step 371can be determined, for example, by determining a time difference betweenthe current waveform zero-crossing and the voltage waveformzero-crossing.

In step 373, real power being consumed is calculated. Real power isdetermined based on the AC voltage measurements from step 371 and the ACcurrent measurements from step 372. In an embodiment, real power iscalculated, for example, at times 0 seconds, 10 seconds, 60 seconds, and600 seconds after an attempt to start the lamp. Other times can also beused.

In step 374, a determination is made whether real power is changingduring an expected startup time of the lamp. If no change in real poweris detected, control passes to step 375 (Bad Lamp). Otherwise, controlpasses to step 371.

In step 375, a signal is generated to indicate that the lamp is bad.

FIG. 3G is a flow chart illustrating the steps of a method 380 fordetecting a bad fixture of a luminaire according to an embodiment of thepresent invention. Method 380 can be implemented by embodiments ofintelligent luminaire manager 112. As shown in FIG. 3G, method 380comprises steps 381-386.

In step 381, the input AC voltage (V.sub.AC) provided to a luminaire ismeasured. In an embodiment, the input AC voltage is preferably measuredat a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The frequency (.omega.) of theinput AC voltage can be determined, for example, by identifying how manyvoltage waveform zero-crossings occur in a selected time interval.

In step 382, the input AC current (I.sub.AC) provided to the luminaireis measured. In an embodiment, the input AC current is also preferablymeasured at a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The phase angle (.theta.)between the measured AC current and the AC voltage measured in step 381can be determined, for example, by determining a time difference betweenthe current waveform zero-crossing and the voltage waveformzero-crossing.

In step 383, real power being consumed is calculated. Real power isdetermined based on the AC voltage measurements from step 381 and the ACcurrent measurements from step 382.

In step 384, a determination is made whether the AC current is less thanor equal to a first threshold value. In one embodiment, a thresholdvalue of about 0.2 amps is used. Other values can also be used. If theAC current is less than or equal to the first threshold value, controlpasses to step 386. Otherwise, control passes to step 385. In anembodiment, a current of less than about 0.2 amps indicates, forexample, either a bad fixture, ballast or a bad starter.

In step 385, a determination is made whether the real power is less thanor equal to a second threshold value. In one embodiment, a thresholdvalue of about 40 watts is used. Other values can also be used. If thereal power is less than or equal to the second threshold value, controlpasses to step 386. Otherwise, control passes to step 381. In anembodiment, a power of less than 40 watts is an indication, for example,of an open ballast, a bad starter, an open lamp, or a broken wire.

In step 386, a signal is generated to indicate that the fixture is bad.

FIG. 3H is a flow chart illustrating the steps of a method 390 forpredicting lamp failure of a luminaire according to an embodiment of thepresent invention. Method 390 is based, for example, on the lamp curvesshown in FIG. 3I below. Method 390 can be implemented by embodiments ofintelligent luminaire manager 112. As shown in FIG. 3H, method 390comprises steps 391-398.

In step 391, the input AC voltage (V.sub.AC) provided to a luminaire ismeasured. In an embodiment, the input AC voltage is preferably measuredat a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The frequency (.omega.) of theinput AC voltage can be determined, for example, by identifying how manyvoltage waveform zero-crossings occur in a selected time interval.

In step 392, the input AC current (I.sub.AC) provided to the luminaireis measured. In an embodiment, the input AC current is also preferablymeasured at a plurality of times (T.sub.i). The time intervals betweenmeasurements can be constant or variable. The phase angle (.theta.)between the measured AC current and the AC voltage measured in step 391can be determined, for example, by determining a time difference betweenthe current waveform zero-crossing and the voltage waveformzero-crossing.

In step 393, real power being consumed is calculated. Real power isdetermined based on the AC voltage measurements from step 391 and the ACcurrent measurements from step 392.

In step 394, a determination is made whether real power is changingafter time T1. In an embodiment, T1 is about 2 minutes. This value isbased on curve A1 in FIG. 3I. Other values can also be used. If realpower is not changing, control passes to step 398. Otherwise, controlpasses to step 391.

In step 395, a determination is made whether real power is changingafter time T2. In an embodiment, T2 is about 6 minutes. This value isbased on curve C1 in FIG. 3I. Other values can also be used. If realpower is changing, control passes to step 398. Otherwise, control passesto step 391.

In step 396, a determination is made whether real power is less than orequal to a threshold value after time T3. In an embodiment, thethreshold value is about 50 watts and T3 is about 6 minutes. These valueare based on curve B1 in FIG. 3I. Other values can also be used. Thethreshold value is selected, for example, based on the power of the lampto be monitored. If real power is less than or equal to the thresholdvalue after time T3, control passes to step 398. Otherwise, controlpasses to step 391.

In step 397, a determination is made whether a DC component ofvoltage/current is greater than or equal to a selected percentage of theAC component of voltage/current. A relatively large DC component ofvoltage/current is an indication of rectification. Lamps usually cycle,however, before rectification problems occur. If the DC component ofvoltage/current is greater than or equal to a selected percentage of theAC component of voltage/current, control passes to step 398. Otherwise,control passes to step 391.

In step 398, a signal is generated to indicate the lamp is about tofail. This signal may also indicate that the wrong type lamp has beeninstalled, if it occurs soon after lamp replacement. If the lamp hasbeen installed and operating properly for a period of time, one candeduce that the correct lamp was initially installed and thus theinstalled lamp is one that is about to fail.

As will be understood by persons skilled in the relevant art, method 390can be modified, for example, to delete one of the depicted predictivetests, such as the DC component test, or to add additional predictivetests.

FIG. 3I is a graph illustrating fixture power as a function of timeduring startup of a gas discharge lamp. As shown in FIG. 3I, the graphis divided into three regions: A, B, and C. Region B representsoperation of lamps, during startup, that still have remaining usefullife. Curve B1 is an example curve showing the startup of a good lamp.Regions A and C represent operation of lamps, during startup, that areabout to fail. Curve A1 represents startup of a lamp that has reachedthe end of its useful life. Curve C1 represents startup of a lamp, forexample, that has a leaking gas tube. As described above, FIG. 3I isuseful for predicting when a lamp is about to fail.

Based on the description of the present invention contained herein, itwill become apparent to persons skilled in the relevant arts that someor all of the functions and/or functionality described with regards tointelligent luminaire manager 112 herein can be implemented, forexample, as an integral part of luminaire 200. Similarly, functionsand/or functionality described with respect to luminaire 200 (e.g.,starter 306) can be implemented as a part of intelligent luminairemanager 112. Thus, the illustration and description of specificfunctions and functionality residing in luminaire 200 and/or intelligentluminaire manager 112 is illustrative and not intended to limit thepresent invention.

FIG. 4A is a more detailed depiction of a network operation center 106according to an embodiment of the present invention. As shown in FIG.4A, network operation center 106 includes a main server 400, a maindatabase 402, data backup 404, and data routing capabilities 406.

As will become apparent from the description herein, network operationcenter 106 provides many services, such as, for example, main datanetwork system operation and maintenance 408, subscriber/customerservices 410, network security services 412, and subscriber/customerdata interface services 414. As used herein, the termsubscriber/customer refers to a light system owner/operator 108 and/or athird party user 110.

In one embodiment, network operation services provided by networkoperation center 106 personnel include six major components: subscriberprovisioning, network provisioning, traffic engineering, billing,service assurance, and security management. Subscriber provisioningrefers to subscriber management, subscriber selection, and subscriberactivation. Network provisioning refers to capacity planning, networkdesign, and device provisioning. Traffic engineering refers to networktraffic analysis and policy management. Billing refers to, for example,both settlement of accounts between and amongst subscriber/customers,and usage data collection, rating, invoicing, and collection of bills.In an embodiment, network operations center 106 records customerinformation for each intelligent luminaire manager 112 that can be usedby owner/operators 108 to support customer service queries and reportsand billing of their respective customers. Service assurance refers toasset management, performance management, service-level management,fault management, trouble management, and work-force management.Security management refers to access fraud, service fraud, managementaccess control, and denial of service. The goal of these networkservices is to provide a framework that provides scalability for aunified wide-area network platform that can be easily managed andcontrolled in real time, for example, over the internet using eitherstandard web browsers or customer-specific applications developed withina software framework. Like the physical hardware of the network, thesoftware is scalable.

Scalability of the system can be ensured by distributing the necessarysoftware over multiple servers. In addition, this increases bothredundancy and reliability. A communications software program maintainedby network operation center 106 provides a virtual private network foreach gateway to the network operation center (e.g., master controllers114). Network operation center 106 is capable of supporting manythousands of concurrent subscribers. Notable features of networkoperation center 106 include its store and forward data managementtechnology; its management environment that supports and controls amassive subscriber base of mobile computers, integrated servers and webservice users; its security and data independence that facilitatessupporting large numbers of separate customers and their sensitivebusiness data; and its ability to provide fast, secure, andhighly-available synchronization between servers and thesubscriber/customer populations they support.

In an embodiment, network operation center 106 is capable, for example,of being scaled to support up to about 120,000 master controllers ormore and up to about 60 million intelligent luminaire manager nodes ormore, which could handle traffic of about 1 megabyte of data per day pergateway or master controller 114.

In an embodiment, network operation center 106 records GPS coordinatesfor each node location (e.g., the locations of intelligent luminairemanagers 112). This data is used to generate user display maps of nodelocations and to support workforce management reports that include nodelocations.

Network operation center 106, based on data collected, also is able toprovide detailed information to its subscribers/customer regarding thetype of fixture, lamp type, ballast type, and starter type operated byeach intelligent luminaire manager 112. Additionally, network operationcenter 106 software is able to generate summary failure analysisreports, broken down by lighting system attributes such as, for example,fixture type, lamp type, ballast type, starter type, and hours ofoperation. This analysis is provided to specific customers and/or allcustomers, based on how often a component fails or requires a servicecall. The analysis preferably includes failure conditions identified bythe network as well as information provided to call centers about thefailures.

In an embodiment, a time stamp is provided with data packet transportedvia a network such that resolution about events on the network can beidentified, for example, within one minute. If a luminaire 200controlled by an intelligent luminaire manager 112 fails, it preferablytakes about one minute in this embodiment before an alarm is generatedat an associated owner/operator's site. This alarm preferably displaysboth the location of the failed luminaire and the time of failure.

As shown in FIG. 4A, network operation center 106 maintains a database402 that includes the current status of all nodes in the data networksystem. In an embodiment, the bandwidth of the network is such that itcan support video. In an embodiment, network operation center 106, viathe networks 102, forwards requests from subscribes/customers forinformation, such as, for example, current voltage levels at monitoreddevices, value of meters, power usage by individual devices, etc.Routine message traffic is preferably scheduled to occur at certainintervals. Examples are network status, device status, abnormal linevoltage, power quality, tilt sensor to alert of pole failure, airquality, road conditions, for example, monitored by a video cameralinked into the network, et cetera. The period of these reportingintervals is programmable (e.g., from one-hour to 24-hour intervals in15 minute increments or less). Event or alarm reporting is preferablyhandled on a priority basis, and it does not conform to a routineforwarding schedule.

In an embodiment, when the alarm data is received at network operationcenter 106, it is compared to predetermined action stored in a program,and the actions are carried out as described. For example, the networkoperation center may send an email to certain individuals, a map showingthe location of the failed device, and/or generate a work order byinterfacing with a subscriber/customer's work-order program. The type ofdata sent from network operations center 106 to a subscriber/customer isnot limited, but in practical terms may be limited in its usefulness toa subscriber/customer based on ability to receive and use the data.

In an embodiment, the message traffic passed between network operationcenter 106 and intelligent luminaire managers 112 includes applicationsdata packages, query command packages, device status packages, event andalarm packages, and network status packages. Subscriber/customer accessto this data stored at the network operation center is controlled bypassword. Subscriber/customer notification of events is transmitted tothe subscriber/customer, and no password is required to obtain thisdata.

In an embodiment, network operation center 106 is able to identify whenthere is a power failure effecting a subscriber/customer's light systemand when backup power is being used at master controls 114. For asystem-wide power outage, network operation center 106 can consolidatealarm reports and generate a generalized message that is forwarded to aneffected subscriber/customer (e.g., a light-system owner/operator 108).

As noted above, in the event of a power failure or a network failuresuch that a master controller 114 cannot provide data to networkoperation center 106 on a scheduled interval, the data is maintained atthe master controller 114 until power and communications are restored.The stored data is then forwarded at the next scheduled reportinginterval, unless specifically requested earlier by a subscriber/customerIn an embodiment, master controller 114 includes battery back-up power.In another embodiment, master controller 114 is capable of transmittingan “I've Lost Power” signal when power is lost.

Network operation center 106 is responsible for IP protocol trafficanalysis. Traffic is routed such that it is able to support peak loadingof the data network and still pass data. In order to manage data,subscriber/customer commands may be limited during certain unexpectedpeak loads and held until bandwidth becomes available to forward thistraffic. When a bandwidth limitation is being reached in a network 102,an alarm is sent to network operation center 106 so that traffic can bemanaged accordingly to control the peak load. Network operation center106 personnel can monitor traffic loading on the network and installadditional capacity as required.

In an embodiment, as noted above, network operation center personnelperform asset management functions, which include tracking the lifecycle of node equipment, and replacing end-of-life equipment or degradedequipment before failure. For light system owner/operators 108, networkoperation center 106 data analysis programs can track the complete lifeof a device (e.g., the time it was installed, the number of hours it wasoperated, and a cause of failure).

Network security services 412 control access to the information storedby network operation center 106 using firewalls and prevent unauthorizedaccess/network usage to prevent compromise of the data and/or network.In an embodiment, network security services 412 require bothauthentication and authorization. Security techniques are implemented toprevent denial-of-service attacks and virus attacks that would cause thenetworks to fail or breakdown. Network security services 412 alsopreferably include intrusion tracking and the ability to trace andcombat malicious acts by unauthorized users. In an embodiment, a “callhome” feature is used such that when a request for information orservice is sent from a subscriber/customer to network operation center106, the request is repeated and sent back to the subscriber/customer'sknown address by network operation center 106 to verify that the requestactually came from that subscriber/customer. Network security services412 also employ and support data encryption.

In an embodiment, network operation center 106 as a part of itssubscriber/customer service provides monthly reports summarizing assetstatus of monitored devices to subscribers/customers. Additionally, inan embodiment, network operation center 106 sends messages to lightsystem managers when a light is turned on and when it is turned off sothat the light system manager can keep track of the present status ofthe light system assets.

FIG. 4B illustrates another embodiment of a network operation centeraccording to the present invention. As shown in FIG. 4B, all thefunctions and functionality of network operation center 106 describedabove need not reside at a single geographical location. Thisfunctionality can be distributed over a wide geographical area. As shownin FIG. 4B, in an embodiment, the functionality of network operationcenter 106 is distributed across a central network operation center(NOC) 420 and one or more regional/customer network operation centers422.

FIG. 5A depicts a light system owner/operator 108. As shown in FIG. 5A,owner/operator 108 is divided into a light system manager portion 109and a maintenance unit portion 111. The light system manager portionincludes a subscriber server 500, a database 502, and a computer display504.

Computer display 504 presents, in both a text and a graphical manner,information about the owner/operator's light system. The text andgraphical information includes, for example, the status of any alarms,power usage, network status, and device status. The status is also showngraphically on a visual map display. In one embodiment, a graphical userinterface presents a visual photometric mapping to a user, for example,of selected lights of the light system. This photometric mapping canprovide the user with a visual representation of the illumination, forexample, of a parking lot, a sports field, or other area of interest.The bottom portion of computer screen 504 shows commands being enteredand responses being received from network operation center 106.

The light system manager preferably has the ability to run severalprograms at his or her site. These programs include alarm andmaintenance (e.g., repair dispatch) program(s) 506, light systemmanagement program(s) 508, billing program(s) 510, data analysisprogram(s) 512, a data storage and retrieval program 514, a networkoperation center interface program 516, and a data routing program 518.Each of these programs is further described below.

Alarm and maintenance program(s) 506 displays an alarm such thatmaintenance personnel 120 can take corrective action. In an embodiment,the program uses data that has been analyzed, for example, by networkoperation center 106 and schedules maintenance so that equipment in thefield close to the end of its useful operating life can be replacedprior to failure. For better predictability, this end of life analysiscan be based on a larger population of equipment than only that ownedand operated by a particular light system manager.

Light management program(s) 508 are used by the light system manager toreprogram devices in the field. Examples of this include, for example,turning lights on and lights off using a schedule rather than havingthem simply turn on at dusk and off at dawn.

Billing program(s) 510 keep track of when specific lights are used andgenerates customer bills accordingly. In one embodiment, the ratecharged for turning on and using a particular light can be based on thetime it is turned on (e.g., during peak hours of operation or off-peakhours of operation).

Data analysis program(s) 512 maintain the state of components in use ina light system and compare, for example, each component's total time inuse to an estimated life expectancy to predict a remaining time tofailure for the component. When a component is at its expected end oflife, the data generated by program(s) 512 can be used to create a workorder to have maintenance personnel 120 replace the component before itfails, for example, by interacting with a maintenance/work order program520.

Data storage and retrieval program(s) 514 facilitate the storage andretrieval of data at the light manager's site in database 502.

Network operating system interface program 516 is used to interface withnetwork operation center 106. This interface program is useful, forexample, for transmitting data to and receiving data from intelligentluminaire managers 112 installed on the light system manager'sequipment.

Data routing program 518 parses and routes data received from networkoperation center 106.

On the maintenance unit side, there is included a maintenance work orderprogram 520, an intelligent luminaire manager field unit interfacedevice 522, and an intelligent luminaire manager field unit 524. Alsoincluded are an inventory purchasing program 526 and an asset managementprogram 528.

In an embodiment, when an alarm or maintenance requirement is sent tothe light system manager by network operation center 106, it isautomatically routed to maintenance/work order program 520. This programthen automatically generates a work order that can be acted upon by amaintenance worker. An electronic copy of the work order can bedownloaded to intelligent luminaire manager field unit 524 viaintelligent luminaire manager field unit interface 522.

In an embodiment, intelligent luminaire manager field unit 524 is ahand-carried portable device that can be taken on-site while installingand/or servicing a luminaire 200. Information about the installationand/or service is captured by intelligent luminaire manager field unit524 for subsequent entry into the records of the light systemowner/operator 108. Upon return of the maintenance worker to themaintenance unit, the collected information is uploaded from the fieldunit into maintenance records. In an embodiment, this uploadedinformation is forwarded to network operation center 106 where it isstored and analyzed along with information gather by maintenance unitsof other light system owner/operators.

In an embodiment, alarms generated by an intelligent luminaire manager112 are not cleared until replacement/service information is received atnetwork operation center 106.

In an embodiment, inventory purchasing program 526 keeps track, forexample, of stock on hand and causes equipment to be ordered and stockedbased on information collected from intelligent luminaire managers 112.

The asset management program 528 is a program that modifies assetmanagement data received, for example, from network operation center 106to satisfy particular light system owner/operator data requirements.

Based on the description of the present invention contained herein, itwill become apparent to persons skilled in the relevant arts that any orall of the functions and/or functionality described with regards tonetwork operation center 106 can be implemented, for example, by a lightsystem owner/operator 108. Similarly, any or all of the functions and/orfunctionality described with respect to a light system owner/operatorcan be implemented by network operation center 106. Thus, theillustration and description of specific functions and functionalityresiding at a particular location or with a particular entity isillustrative and not intended to limit the present invention.

FIG. 5B further illustrates intelligent luminaire manager field unit524. Field unit 524 is used, for example, to activate newly installed orserviced intelligent luminaire managers 112.

In an embodiment, field unit 524 includes an on-board GPS system 534 anda communications interface 536. The communications interface cancommunicate, for example, with an intelligent luminaire manager or otherdevice using RF and/or optical communications. Using the GPS 534, thefield unit identifies the location where an intelligent luminairemanager 112 is installed. This information is stored, for example, inmemory 320 of intelligent luminaire manager 112. It is also taken backto the maintenance unit and stored in the maintenance unit's records.Additionally, it is forwarded to network operation center 106 via thelight manager's subscriber/customer interface to network operationcenter 106. Other information collected and forwarded to networkoperation center 106 includes, for example, all the particulars aboutthe equipment monitored and controlled by the intelligent luminairemanager 112 (e.g., lamp type, ballast type, digital photo, etc.).

In embodiments of the present invention, for example where more than oneintelligent luminaire manager 112 may be installed at the samegeographical location (e.g., in a situation where two luminaires areattached to a single pole and each luminaire has its own intelligentluminaire manager 112), field unit 524 can be used to assign a uniqueidentification value to each of the luminaire managers.

Once an intelligent luminaire manager 112 is installed, itself-configures by running a configuration program. Once alive, network102 notifies network operation center 106, via master controller 114,that a new device has entered the network.

In an embodiment, field unit 524 is hosted by a PDA 530, runningapplication program(s) 532. The present invention is not limited,however, to requiring the use of a PDA. Map base reports downloaded tofield unit 524 show the location of each luminaire in a light system anddisplay efficient driving routes for maintenance crews to get to aluminaire requiring repair. Fault types are communicated to crews vianetwork operation center 106 and field unit 524 for pre-diagnostics of afailed luminaire so that time on-site is minimized and the need forreturn trips to a failed luminaire are eliminated. In an embodiment, thetype of faults and corrective actions that can be provided tomaintenance crew workers include anticipated lamp cycling, lamp cycling,no starting pulse, starting pulse but failed to start, non-reportingunit, replace lamp when traveling to area, replace lamp, replacestarter, check power at fixture, if no power repair power, and if powerreplace intelligent luminaire manager unit. As will be understood bypersons skilled in the relevant arts, this list is illustrative and notintended to limit the present invention.

It is a feature of the present invention that during activation of a newintelligent luminaire manager 112, each unit is identified both in termsof its type of luminaire and its GPS location. This data, coupled withthe failure mode reporting, allows for a much greater maintenance crewefficiency. Additionally, dedicated, less-costly maintenance crews areable to conduct all maintenance during daylight hours, rather thannighttime, at significantly lower cost.

In an embodiment, when an intelligent luminaire manager 112 is removedfrom service, its identification number is captured by field unit 524.If the GPS coordinates of the removed intelligent luminaire manager 112differ from what is expected (e.g., by more than a couple of meters) analert/alarm is generated or initiated by field unit 524 and preferablyprovided to network operation center 106. The alarm is an indication,for example, that (1) the removed intelligent luminaire manager 112 wasoriginally installed improperly (e.g., at the wrong location or with thewrong GPS coordinates); (2) the removed intelligent luminaire manager112 has been moved since its activation without proper authority; or (3)the data stored by the removed intelligent luminaire manager 112 hasbeen corrupted.

While the foregoing is a complete description of exemplary embodimentsof the invention, it should be evident that various modifications,alternatives and equivalents may be made and used. For example, althoughthe intelligent luminaire manager of the present invention is describedas controlling luminaires having conventional lamps, it will be apparentto individuals skilled in the relevant arts given the description hereinthat the intelligent luminaire manager can be adapted to manage othertypes of lighting such as, for example, light emitting diodes. Inaddition, the intelligent luminaire manager of the present invention canalso be adapted to manage other electromechanical devices. Thus, it isnot limited to managing only luminaires. Accordingly, the abovedescription should not be taken as limiting the scope of the invention.

1. A method for managing a plurality of luminaires, comprising:receiving, by a network operation center via one or more mastercontrollers, information for a plurality of luminaires from a pluralityof networked intelligent luminaire managers, each networked intelligentluminaire manager being coupled to an associated luminaire andconfigured to monitor and communicate a status of the associatedluminaire; storing, by the network operation center, the receivedinformation; and routing, by the network operation center, receivedinformation for a first group of luminaires to a first computerassociated with an operator of the first group of luminaires, whereinthe network operation center comprises one or more servers.
 2. Themethod of claim 1, further comprising: routing, by the network operationcenter via one or more master controllers, information for a secondgroup of luminaires to a second computer associated with an operator ofthe second group of luminaires.
 3. The method of claim 1, furthercomprising: receiving, by the network operation center, a command fromthe computer associated with the operator of the first group ofluminaires to turn-on or turn-off a particular luminaire; storing, bythe network operation center, the command; and routing, by the networkoperation center via one or more master controllers, the command to thenetworked intelligent luminaire manager coupled to the particularluminaire.
 4. The method of claim 1, wherein the received informationincludes information about usage of each luminaire, further comprising:generating, by the network operation center, a bill for a particulargroup of luminaires based on the received information.
 5. The method ofclaim 1, further comprising: adjusting a flow of communications betweenselected networked intelligent luminaire managers.
 6. The method ofclaim 1, further comprising: sending, by the network operation center,an alarm to the first computer associated with the operator of the firstgroup of luminaires if status information is received indicating that aparticular luminaire of the first group of luminaires is not functioningproperly.
 7. The method of claim 6, wherein the sending step comprisesat least one of: (i) sending location information for the particularluminaire, (ii) sending time of failure information for the particularluminaire, or (iii) sending type of failure information for theparticular luminaire.
 8. The method of claim 1, further comprising:analyzing, by the network operation center, the received information;and generating, by the network operation center a report based on theanalysis.
 9. The method of claim 8, wherein the generating stepcomprises: generating a failure analysis report.
 10. The method of claim1, further comprising: sending billing information to the first computerassociated with the operator of the first group of luminaires.
 11. Themethod of claim 1, further comprising: sending network statusinformation to the first computer associated with the operator of thefirst group of luminaires.
 12. The method of claim 1, furthercomprising: sending power usage information to the first computerassociated with the operator of the first group of luminaires.
 13. Amethod for managing a plurality of luminaires, comprising: receiving, bya network operation center via one or more master controllers,information for a plurality of luminaires from a plurality of networkedintelligent luminaire managers, each networked intelligent luminairemanager being coupled to an associated luminaire and configured tomonitor and communicate a status of the associated luminaire; routing,by the master controller or the network operation center, informationfor a first group of luminaires to a first computer associated with anoperator of the first group of luminaires; receiving, by the networkoperation center, a command from the first computer associated with theoperator of the first group of luminaires to turn on turn-on or turn-offa particular luminaire; and routing, by the network operation center viaone or more master controllers, the command to the networked intelligentluminaire manager coupled to the particular luminaire, thereby enablingthe networked intelligent luminaire manager to turn-on or turn-off theparticular luminaire, wherein the network operation center comprises oneor more servers.
 14. The method of claim 13, further comprising:sending, by the network operation center, an alarm to the first computerassociated with the operator of the first group of luminaires ifinformation is received indicating that a particular luminaire of thefirst group of luminaires is not functioning properly.
 15. The method ofclaim 14, wherein the sending step comprises: sending locationinformation for the particular luminaire; and sending time of failureinformation for the particular luminaire.
 16. The method of claim 13,further comprising: adjusting a flow of communications between selectednetworked intelligent luminaire managers.
 17. The method of claim 13,further comprising: analyzing, by the network operation center, thereceived information; and sending, by the network operation center, areport based on the analysis to the first computer associated with theoperator of the first group of luminaires.
 18. A system, comprising: adatabase, and at least one server, wherein the at least one server isconfigured to: receive, via one or more master controllers, informationfor a plurality of luminaires from a plurality of networked intelligentluminaire managers, each networked intelligent luminaire manager beingcoupled to an associated luminaire and configured to monitor andcommunicate a status of the associated luminaire; store, in thedatabase, the received information; and route the received informationfor a first group of luminaires to a first computer associated with anoperator of the first group of luminaires.
 19. The system of claim 18,wherein the at least one server is further configured to: receive acommand from the computer associated with the operator of the firstgroup of luminaires to turn-on or turn-off a particular luminaire;store, in the database, the command; and route, via one or more mastercontrollers, the command to the networked intelligent luminaire managercoupled to the particular luminaire.
 20. The system of claim 18, whereinthe received information includes information about usage of eachluminaire, and wherein the at least one server is further configured to:generate a bill for a particular group of luminaires based on thereceived information.